@sanity
Feature: Rail order and ops rail order timehseet functionalities
File name: laborOrder_rail.feature
Relative path: features/laborOrder_rail.feature
Given
TR user logged into the application
Given
the user creates a new Rail order
Then
the user discards the Rail order
Given
TR user logged into the application
Then
Verify that the appropriate validation message for start time field in rail order
Then
Verify that the appropriate validation message for steady name and steady count field in rail order
Given
TR user logged into the application
Given
the user creates a new Rail order
Then
the user firm the Rail order
Then
the user push the Rail labor order to the summary sheet
Then
the user cancel the Rail order
@sanity
Scenario: TR user creates a rail order timesheet and verifies save without submit, save and submit, and download report functionalities
Given
TR user logged into the application
Given
the user creates a new Rail order
Then
the user push the Rail labor order to the summary sheet
Given
the user creates a new rail timesheet
When
the user saves the rail order without submitting it
Then
the user saves and submits the rail order
Then
user click on logout button
Then
Ops user logged into the application
Then
Ops user submits and approve the rail order timesheet
Then
ops user reject the rail timesheet
Then
verify remove approval functionality in rail timehseet
Then
user click on logout button
Then
Timehseet entry user logged into the application
Then
Labor entry add new steady details and mgr comments and submit the rail order timehseet
Then
user click on logout button
Then
Ops user logged into the application
Then
Ops user submits and approve the rail order timesheet
Then
the user verifies the download report functionality for the rail order
Then
user click on logout button
